Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8039cf8340f3d2329eee90fbb991712eecfdde8be08e685c0cb403c541dfa1c1

Tx prefix hash: fc74d637f1e3d2582d99500a5d62ea7a5b3081d8ee8f8df362eb41d8847a2d80
Tx public key: 7d694b36d21f52c2090deaba9c7c1904e0ebd1dae686a60e5a63290df96673c3
Timestamp: 1715383194 Timestamp [UCT]: 2024-05-10 23:19:54 Age [y:d:h:m:s]: 00:321:09:27:02
Block: 1019297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229706 RingCT/type: yes/0
Extra: 017d694b36d21f52c2090deaba9c7c1904e0ebd1dae686a60e5a63290df96673c3021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d721a4aeccef0628239ac14b4ef6803e2e7db5c46c34e41b88f67d8fe094a3e 0.600000000000 1483226 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": 1019307, "vin": [ { "gen": { "height": 1019297 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d721a4aeccef0628239ac14b4ef6803e2e7db5c46c34e41b88f67d8fe094a3e" } } ], "extra": [ 1, 125, 105, 75, 54, 210, 31, 82, 194, 9, 13, 234, 186, 156, 124, 25, 4, 224, 235, 209, 218, 230, 134, 166, 14, 90, 99, 41, 13, 249, 102, 115, 195, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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