Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 955dafc944c37bfb8d92be6e0d798ea4c70f09dae03f3b6905c2ff46f19de674

Tx prefix hash: 79594f3c997cee7a399552a2ae3271f5b12c01979f2840b40b645388530a6d05
Tx public key: 97a382f003513fad299e40513b39c3b40db83beca8fe99265ef07dd5a8493d84
Timestamp: 1727258640 Timestamp [UCT]: 2024-09-25 10:04:00 Age [y:d:h:m:s]: 00:059:21:32:08
Block: 1117732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42809 RingCT/type: yes/0
Extra: 0197a382f003513fad299e40513b39c3b40db83beca8fe99265ef07dd5a8493d8402110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbf253008390a1c8a4de1bb7b4c6382cd5dd1fd030eaf3d6b6ae03ece569bdf3 0.600000000000 1598675 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": 1117742, "vin": [ { "gen": { "height": 1117732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbf253008390a1c8a4de1bb7b4c6382cd5dd1fd030eaf3d6b6ae03ece569bdf3" } } ], "extra": [ 1, 151, 163, 130, 240, 3, 81, 63, 173, 41, 158, 64, 81, 59, 57, 195, 180, 13, 184, 59, 236, 168, 254, 153, 38, 94, 240, 125, 213, 168, 73, 61, 132, 2, 17, 0, 0, 0, 6, 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