Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63268644b5a19a25df0495e465dc7f8e96065d8f5836cf24290b3a2c04924d44

Tx prefix hash: 06ab2ff0b9b01ce0cd14192ac4038e6e2ad1522bf051490e0223b00c913dc56b
Tx public key: e4eb4f2f5b665344db3e710866398e8d4f56bff23507c4f42c95d79c81739f22
Timestamp: 1725687064 Timestamp [UCT]: 2024-09-07 05:31:04 Age [y:d:h:m:s]: 00:259:11:34:55
Block: 1104701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185336 RingCT/type: yes/0
Extra: 01e4eb4f2f5b665344db3e710866398e8d4f56bff23507c4f42c95d79c81739f2202110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47555606851dcb17b2bfffe77b2f10a5697f0a4b83b6051646960f23d623f62d 0.600000000000 1581944 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": 1104711, "vin": [ { "gen": { "height": 1104701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47555606851dcb17b2bfffe77b2f10a5697f0a4b83b6051646960f23d623f62d" } } ], "extra": [ 1, 228, 235, 79, 47, 91, 102, 83, 68, 219, 62, 113, 8, 102, 57, 142, 141, 79, 86, 191, 242, 53, 7, 196, 244, 44, 149, 215, 156, 129, 115, 159, 34, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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