Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 415d7701939c58a80b3dbbbd201edbf50e7c0f715a1bb9412135612921c17a3d

Tx prefix hash: fc3ebc726303d801adb8840ce07e33d9e746521f93821422d3b8b38e601fa524
Tx public key: b1935f23e4010a86590e4e6483b1fc9877b41a6f6b48335a1eeb0458f1cf1018
Timestamp: 1720616730 Timestamp [UCT]: 2024-07-10 13:05:30 Age [y:d:h:m:s]: 00:250:14:40:53
Block: 1062670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179046 RingCT/type: yes/0
Extra: 01b1935f23e4010a86590e4e6483b1fc9877b41a6f6b48335a1eeb0458f1cf101802110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6b6ad06339a53fb2693a277e9f1f06e714ee8880c02b4ad93c15dff110b21c5 0.600000000000 1533177 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": 1062680, "vin": [ { "gen": { "height": 1062670 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6b6ad06339a53fb2693a277e9f1f06e714ee8880c02b4ad93c15dff110b21c5" } } ], "extra": [ 1, 177, 147, 95, 35, 228, 1, 10, 134, 89, 14, 78, 100, 131, 177, 252, 152, 119, 180, 26, 111, 107, 72, 51, 90, 30, 235, 4, 88, 241, 207, 16, 24, 2, 17, 0, 0, 0, 8, 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