Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39524e37ceba5ec11ddce8c7853d352017bb6f7dbd03b452b00ecc6d43a777b5

Tx prefix hash: 8142dea6b26ea451f62cfc92251d8c124959b4858c3d195e5af2b6f0167d311c
Tx public key: 05cd1b9e57c5fb2a3ea3adf712a00f7eb72acb06af06e790a13d32a0b76b865f
Timestamp: 1722679322 Timestamp [UCT]: 2024-08-03 10:02:02 Age [y:d:h:m:s]: 01:066:14:18:22
Block: 1079766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306034 RingCT/type: yes/0
Extra: 0105cd1b9e57c5fb2a3ea3adf712a00f7eb72acb06af06e790a13d32a0b76b865f021100000009e914dd15000000000000000000

1 output(s) for total of 0.615610000000 dcy

stealth address amount amount idx
00: c873fcdac2b82d3ff9c613d53cbb14200fa97698f1f2fd3a17ec9be7ee235c05 0.615610000000 1552863 of 0

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": 1079776, "vin": [ { "gen": { "height": 1079766 } } ], "vout": [ { "amount": 615610000, "target": { "key": "c873fcdac2b82d3ff9c613d53cbb14200fa97698f1f2fd3a17ec9be7ee235c05" } } ], "extra": [ 1, 5, 205, 27, 158, 87, 197, 251, 42, 62, 163, 173, 247, 18, 160, 15, 126, 183, 42, 203, 6, 175, 6, 231, 144, 161, 61, 50, 160, 183, 107, 134, 95, 2, 17, 0, 0, 0, 9, 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