Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9267ce2f2f70bcf40b55d07fb3d64adbbb03a0e6bd8798de53275512c352417

Tx prefix hash: 97012a526373c369d938cc555eda38e096e6aefadc2b6971b614ad68b85ce3f4
Tx public key: ed3931f92b77c7dd4ddd324a3c7a951fb6b0aaf0a7cd5e177fe0d1d954cf06bb
Timestamp: 1695644665 Timestamp [UCT]: 2023-09-25 12:24:25 Age [y:d:h:m:s]: 01:242:01:03:53
Block: 855836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 434090 RingCT/type: yes/0
Extra: 01ed3931f92b77c7dd4ddd324a3c7a951fb6b0aaf0a7cd5e177fe0d1d954cf06bb021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.895901174000 dcy

stealth address amount amount idx
00: 2477e589a296b714fb735cd0c7cf748a05c464c8fdd34e23cccc2e961ed53d8e 0.895901174000 1309884 of 0

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": 855846, "vin": [ { "gen": { "height": 855836 } } ], "vout": [ { "amount": 895901174, "target": { "key": "2477e589a296b714fb735cd0c7cf748a05c464c8fdd34e23cccc2e961ed53d8e" } } ], "extra": [ 1, 237, 57, 49, 249, 43, 119, 199, 221, 77, 221, 50, 74, 60, 122, 149, 31, 182, 176, 170, 240, 167, 205, 94, 23, 127, 224, 209, 217, 84, 207, 6, 187, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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