Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 1cd4d34e98d42ef66ebf040c34c2c605f56c68d086e4abca7284dfe1cb5dd7dd

Tx prefix hash: baa712246676b7d2c000e932cb7bfcfcc128069fa4415088f169c0ceb9fdc28a
Tx public key: f63f75ba621b8b9757a5a164ad44d1efb04d53c6ae7371ec8a63e59935a9c20d
Timestamp: 1644719678 Timestamp [UCT]: 2022-02-13 02:34:38 Age [y:d:h:m:s]: 03:261:18:31:55
Block: 437428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 964757 RingCT/type: yes/0
Extra: 01f63f75ba621b8b9757a5a164ad44d1efb04d53c6ae7371ec8a63e59935a9c20d021100000001d3fcec30000000000000000000

1 output(s) for total of 21.808196325000 dcy

stealth address amount amount idx
00: 0f1ec3cbe134b51c7b493b017efebc5acd0d299b88301336f4b3e43fa92f1905 21.808196325000 849055 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 437438, "vin": [ { "gen": { "height": 437428 } } ], "vout": [ { "amount": 21808196325, "target": { "key": "0f1ec3cbe134b51c7b493b017efebc5acd0d299b88301336f4b3e43fa92f1905" } } ], "extra": [ 1, 246, 63, 117, 186, 98, 27, 139, 151, 87, 165, 161, 100, 173, 68, 209, 239, 176, 77, 83, 198, 174, 115, 113, 236, 138, 99, 229, 153, 53, 169, 194, 13, 2, 17, 0, 0, 0, 1, 211, 252, 236, 48, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8