Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1bd5499d581927585c402e00333ae3ed72cd549a4ff833943c2f2179a6e24c9

Tx prefix hash: b992e7ec407526c34dd5747162c34c794527c1db29c546be53a9c753b8f93d15
Tx public key: 6082a0f437dffaf3ef89c1f9e5378a95e7aec127058a677ea4648244cb0454c0
Timestamp: 1582433684 Timestamp [UCT]: 2020-02-23 04:54:44 Age [y:d:h:m:s]: 05:056:11:40:07
Block: 70570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1193692 RingCT/type: yes/0
Extra: 016082a0f437dffaf3ef89c1f9e5378a95e7aec127058a677ea4648244cb0454c0021100000001724f989b000000000000000000

1 output(s) for total of 358.239192948000 dcy

stealth address amount amount idx
00: b44feb9165647e413c33c742ded3c34c67b85aeeb5fb38f8ce7d784d6ca53597 358.239192948000 130416 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": 70580, "vin": [ { "gen": { "height": 70570 } } ], "vout": [ { "amount": 358239192948, "target": { "key": "b44feb9165647e413c33c742ded3c34c67b85aeeb5fb38f8ce7d784d6ca53597" } } ], "extra": [ 1, 96, 130, 160, 244, 55, 223, 250, 243, 239, 137, 193, 249, 229, 55, 138, 149, 231, 174, 193, 39, 5, 138, 103, 126, 164, 100, 130, 68, 203, 4, 84, 192, 2, 17, 0, 0, 0, 1, 114, 79, 152, 155, 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