Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77ac4b1a0c4f417230595438b8b8f5e9d7effd0be25e74b8034ff45cb0904c27

Tx prefix hash: 38f9d7091163302334ad3aefca4385afc68fff3fbe571c838ef0d40fe509380e
Tx public key: cc358d726f0fd1b95b863a32c06838241ae4deb32371cd8bd77d8013160f93a9
Timestamp: 1711036122 Timestamp [UCT]: 2024-03-21 15:48:42 Age [y:d:h:m:s]: 01:054:13:44:47
Block: 983265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299986 RingCT/type: yes/0
Extra: 01cc358d726f0fd1b95b863a32c06838241ae4deb32371cd8bd77d8013160f93a902110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d6b547fa4c9b2591c7a340f5cbd81a4775d0a6b310445bb5ae39f826c9d7642 0.600000000000 1443392 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": 983275, "vin": [ { "gen": { "height": 983265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d6b547fa4c9b2591c7a340f5cbd81a4775d0a6b310445bb5ae39f826c9d7642" } } ], "extra": [ 1, 204, 53, 141, 114, 111, 15, 209, 185, 91, 134, 58, 50, 192, 104, 56, 36, 26, 228, 222, 179, 35, 113, 205, 139, 215, 125, 128, 19, 22, 15, 147, 169, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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