Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ca2d983ef1e23b916b2983072c72246e928ea9975f57e0cdc89509992f57872

Tx prefix hash: fb6ccb5e6d58bc36951bd4ae16304ce9e11819165c59a2b9fd967edb029f852d
Tx public key: 315fa258c23251d0aa7615e87592dc794473dee33f60ad91df42a1d5c522b7ba
Timestamp: 1702041117 Timestamp [UCT]: 2023-12-08 13:11:57 Age [y:d:h:m:s]: 01:079:14:23:25
Block: 908660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318003 RingCT/type: yes/0
Extra: 01315fa258c23251d0aa7615e87592dc794473dee33f60ad91df42a1d5c522b7ba02110000000833af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01f708dfefda8aa69a822f08f1fe02721c6dd04ca285466ff79125f8ec156fd7 0.600000000000 1365705 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": 908670, "vin": [ { "gen": { "height": 908660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01f708dfefda8aa69a822f08f1fe02721c6dd04ca285466ff79125f8ec156fd7" } } ], "extra": [ 1, 49, 95, 162, 88, 194, 50, 81, 208, 170, 118, 21, 232, 117, 146, 220, 121, 68, 115, 222, 227, 63, 96, 173, 145, 223, 66, 161, 213, 197, 34, 183, 186, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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