Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd20602830e363705e6262ac8f09b9cac453fda06b16096fd70df1e9a7058c01

Tx prefix hash: 8160d74e8b2590c5881dc775eace4d76c6e97070a9b25f6388df493b35cc2f17
Tx public key: 0ff9a4e3e78400607e633b354a3598158cc2cb8f573550d35cd8b9f8669da317
Timestamp: 1722982045 Timestamp [UCT]: 2024-08-06 22:07:25 Age [y:d:h:m:s]: 00:170:00:17:54
Block: 1082270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121590 RingCT/type: yes/0
Extra: 010ff9a4e3e78400607e633b354a3598158cc2cb8f573550d35cd8b9f8669da317021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4639365faf1d4d6e0fcf242b6bc42d70f24e94d2643f72e1b1dea53a35e6e99 0.600000000000 1556095 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": 1082280, "vin": [ { "gen": { "height": 1082270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4639365faf1d4d6e0fcf242b6bc42d70f24e94d2643f72e1b1dea53a35e6e99" } } ], "extra": [ 1, 15, 249, 164, 227, 231, 132, 0, 96, 126, 99, 59, 53, 74, 53, 152, 21, 140, 194, 203, 143, 87, 53, 80, 211, 92, 216, 185, 248, 102, 157, 163, 23, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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