Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c35ac09bfaec7cdf39d1ad963b72a5fca55e2fb56414942fa93847267658392

Tx prefix hash: e6dfc858354f5e0491e798e1720765aeb4807be3b085a547e84754111ec8b85e
Tx public key: e0982da70c79c6e92d1e26c4a603f162bfec47b1391bb00f6a4a6873aecc2557
Timestamp: 1728601410 Timestamp [UCT]: 2024-10-10 23:03:30 Age [y:d:h:m:s]: 00:168:17:09:14
Block: 1128870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120352 RingCT/type: yes/0
Extra: 01e0982da70c79c6e92d1e26c4a603f162bfec47b1391bb00f6a4a6873aecc255702110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf76bf053aa6d3f1b25a183ba153c1e37c607ad1a281f26b572bfeb6cf63b2eb 0.600000000000 1611693 of 15

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": 1128880, "vin": [ { "gen": { "height": 1128870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf76bf053aa6d3f1b25a183ba153c1e37c607ad1a281f26b572bfeb6cf63b2eb" } } ], "extra": [ 1, 224, 152, 45, 167, 12, 121, 198, 233, 45, 30, 38, 196, 166, 3, 241, 98, 191, 236, 71, 177, 57, 27, 176, 15, 106, 74, 104, 115, 174, 204, 37, 87, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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