Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef65ef7e1b07c683002ad4a4811ec2dd437739ffc12dcd124aaf2f4131fc4238

Tx prefix hash: a204d9cc48437dcb5f8abc7f7c81dc81f1aa7fd8fb838dcf310d1367b2eacb3a
Tx public key: 740d24c08a96b1d8948cf9a66b0bdff6f5e2e66ba8ead664c7c697d802886212
Timestamp: 1731000664 Timestamp [UCT]: 2024-11-07 17:31:04 Age [y:d:h:m:s]: 00:151:11:14:19
Block: 1148672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108066 RingCT/type: yes/0
Extra: 01740d24c08a96b1d8948cf9a66b0bdff6f5e2e66ba8ead664c7c697d8028862120211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21276f33a6f2d1608ed0b11b38c6aeb002700f02b226ad8af7b163204e266ab3 0.600000000000 1633575 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": 1148682, "vin": [ { "gen": { "height": 1148672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21276f33a6f2d1608ed0b11b38c6aeb002700f02b226ad8af7b163204e266ab3" } } ], "extra": [ 1, 116, 13, 36, 192, 138, 150, 177, 216, 148, 140, 249, 166, 107, 11, 223, 246, 245, 226, 230, 107, 168, 234, 214, 100, 199, 198, 151, 216, 2, 136, 98, 18, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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