Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c794b64b1acf35c3578b1c8e421c01843d5be927a7cff0c4b48ad3ced1a5765

Tx prefix hash: a2a66435fb6557aa97ce9116e3e2867892aa2e6aa6834153ed6100f60c6d0199
Tx public key: 34fca22c9d409b7f03629effce4ae7938806a19d774309df455a9e9b035f62c5
Timestamp: 1729540582 Timestamp [UCT]: 2024-10-21 19:56:22 Age [y:d:h:m:s]: 00:000:21:45:21
Block: 1136614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 651 RingCT/type: yes/0
Extra: 0134fca22c9d409b7f03629effce4ae7938806a19d774309df455a9e9b035f62c5021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ea760f6ec75e2fbfb4c8e4de380bcc0fec58de3f8c9cc0a36ccbeb3f0e10209 0.600000000000 1619961 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": 1136624, "vin": [ { "gen": { "height": 1136614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ea760f6ec75e2fbfb4c8e4de380bcc0fec58de3f8c9cc0a36ccbeb3f0e10209" } } ], "extra": [ 1, 52, 252, 162, 44, 157, 64, 155, 127, 3, 98, 158, 255, 206, 74, 231, 147, 136, 6, 161, 157, 119, 67, 9, 223, 69, 90, 158, 155, 3, 95, 98, 197, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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