Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96d66ccfbb7ce83d7ecf86f818f2062704313bb074c8c8f80d632239cf4ed52d

Tx prefix hash: f67f07f91db3f2f50bad4005d1f724ffcde8c69e999d36501237943f8ab9a4ae
Tx public key: a93201fd56f07b0d3773d37b3b1eebb4b0369b1ec46093e11ba43f65262f58a0
Timestamp: 1702442117 Timestamp [UCT]: 2023-12-13 04:35:17 Age [y:d:h:m:s]: 01:135:18:06:43
Block: 912011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358161 RingCT/type: yes/0
Extra: 01a93201fd56f07b0d3773d37b3b1eebb4b0369b1ec46093e11ba43f65262f58a002110000000775e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9652dde94c8d77535b8ffeb42de0e2d2843ce1e8efefc510cb0e0244e14e220e 0.600000000000 1369229 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": 912021, "vin": [ { "gen": { "height": 912011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9652dde94c8d77535b8ffeb42de0e2d2843ce1e8efefc510cb0e0244e14e220e" } } ], "extra": [ 1, 169, 50, 1, 253, 86, 240, 123, 13, 55, 115, 211, 123, 59, 30, 235, 180, 176, 54, 155, 30, 196, 96, 147, 225, 27, 164, 63, 101, 38, 47, 88, 160, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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