Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d9a40cf0bca75eb236a7354618de2ff8999bd1b475c4c534f9cf512cc621f10

Tx prefix hash: 5060055b0320bdf7db9b7992eac7c13a79815f43f9f2641e2e6caf33dc441c4d
Tx public key: 28130a057980782f6c283996c86eef7a8d0d630620e55af8efb717c6a137e83b
Timestamp: 1734747807 Timestamp [UCT]: 2024-12-21 02:23:27 Age [y:d:h:m:s]: 00:103:17:51:51
Block: 1179731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73900 RingCT/type: yes/0
Extra: 0128130a057980782f6c283996c86eef7a8d0d630620e55af8efb717c6a137e83b021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: afa3701e4e7f5372ace6d44dbc148cde2c0350901998da7336b7c730f7764ab0 0.600000000000 1666130 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": 1179741, "vin": [ { "gen": { "height": 1179731 } } ], "vout": [ { "amount": 600000000, "target": { "key": "afa3701e4e7f5372ace6d44dbc148cde2c0350901998da7336b7c730f7764ab0" } } ], "extra": [ 1, 40, 19, 10, 5, 121, 128, 120, 47, 108, 40, 57, 150, 200, 110, 239, 122, 141, 13, 99, 6, 32, 229, 90, 248, 239, 183, 23, 198, 161, 55, 232, 59, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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