Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0cfc4855142b8d9d872c198adddbd2383dd3a3ed3c967922d0bb5a2f01e4d95

Tx prefix hash: 8762d5847d9ee6afdddaa1c2a4c7c037384e697021664280f84cb94e282662c0
Tx public key: e03fef11b7f2ead5f95b78ac8160d6081f458e9bb77dfba4e982ec45f710b528
Timestamp: 1577888717 Timestamp [UCT]: 2020-01-01 14:25:17 Age [y:d:h:m:s]: 05:063:21:30:55
Block: 36376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1195561 RingCT/type: yes/0
Extra: 01e03fef11b7f2ead5f95b78ac8160d6081f458e9bb77dfba4e982ec45f710b528021100000058c5b5978f000000000000000000

1 output(s) for total of 465.033583341000 dcy

stealth address amount amount idx
00: c5fb091d60b12de61f226f976cdd3bafe135539817e3b397d45c69412ec7bde5 465.033583341000 61606 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": 36386, "vin": [ { "gen": { "height": 36376 } } ], "vout": [ { "amount": 465033583341, "target": { "key": "c5fb091d60b12de61f226f976cdd3bafe135539817e3b397d45c69412ec7bde5" } } ], "extra": [ 1, 224, 63, 239, 17, 183, 242, 234, 213, 249, 91, 120, 172, 129, 96, 214, 8, 31, 69, 142, 155, 183, 125, 251, 164, 233, 130, 236, 69, 247, 16, 181, 40, 2, 17, 0, 0, 0, 88, 197, 181, 151, 143, 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