Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d37dd39a7e8b1de6131e26527f093327b5c54a80fb52829cf05795b5046a339

Tx prefix hash: ac8d2cf38e06cda4ae501a625998e8083bccedfffddcf2a2ae4e0c0c9b0f7e9c
Tx public key: fc780e298a6a384e15f4cadfe5f6d37000485074c8e05c6869a770f7ddf30efd
Timestamp: 1743551145 Timestamp [UCT]: 2025-04-01 23:45:45 Age [y:d:h:m:s]: 00:233:18:03:57
Block: 1252308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164796 RingCT/type: yes/0
Extra: 01fc780e298a6a384e15f4cadfe5f6d37000485074c8e05c6869a770f7ddf30efd02110000000b4060f6d2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85801d5881344c28f2a6748ca928edc3a5c6a507a08c0747b73bb643895bed8d 0.600000000000 1739389 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": 1252318, "vin": [ { "gen": { "height": 1252308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85801d5881344c28f2a6748ca928edc3a5c6a507a08c0747b73bb643895bed8d" } } ], "extra": [ 1, 252, 120, 14, 41, 138, 106, 56, 78, 21, 244, 202, 223, 229, 246, 211, 112, 0, 72, 80, 116, 200, 224, 92, 104, 105, 167, 112, 247, 221, 243, 14, 253, 2, 17, 0, 0, 0, 11, 64, 96, 246, 210, 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