Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25f9c3282b8de4f0c81386c9a320fd698229d3469c2b5f05b0c1edfb8a1e2a14

Tx prefix hash: 16f9f79e5b8962f859609877db2da621d282f60476503a188b33ed7dbf784237
Tx public key: 66aec941404132d0b210f984c04a515079ded7756e0cfbf3f74e41f0301752d1
Timestamp: 1729027397 Timestamp [UCT]: 2024-10-15 21:23:17 Age [y:d:h:m:s]: 00:232:18:30:55
Block: 1132397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166196 RingCT/type: yes/0
Extra: 0166aec941404132d0b210f984c04a515079ded7756e0cfbf3f74e41f0301752d1021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3aeb2120505ef1b85c343d4f8e2b80ba99e95b5587e241719ba703a1e503315d 0.600000000000 1615310 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": 1132407, "vin": [ { "gen": { "height": 1132397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3aeb2120505ef1b85c343d4f8e2b80ba99e95b5587e241719ba703a1e503315d" } } ], "extra": [ 1, 102, 174, 201, 65, 64, 65, 50, 208, 178, 16, 249, 132, 192, 74, 81, 80, 121, 222, 215, 117, 110, 12, 251, 243, 247, 78, 65, 240, 48, 23, 82, 209, 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