Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de23b2d018108c9eb299ee5b5c188c263d1618627c62857fde439496b7f3c5fe

Tx prefix hash: c176fcda9f6cc30568e06377fc98d03fd1e5912bb9d037df8f2819bae8cd888c
Tx public key: e9147ab1a78582905a7a6fdc92da274c724b03cf376a1d88e35c873ebe173e43
Timestamp: 1713371926 Timestamp [UCT]: 2024-04-17 16:38:46 Age [y:d:h:m:s]: 00:314:07:17:04
Block: 1002603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224664 RingCT/type: yes/0
Extra: 01e9147ab1a78582905a7a6fdc92da274c724b03cf376a1d88e35c873ebe173e4302110000000e52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b742697d53bd61076a37e4b0fee75d11441edf616b017954ae1dba4ca1852ef4 0.600000000000 1463121 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": 1002613, "vin": [ { "gen": { "height": 1002603 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b742697d53bd61076a37e4b0fee75d11441edf616b017954ae1dba4ca1852ef4" } } ], "extra": [ 1, 233, 20, 122, 177, 167, 133, 130, 144, 90, 122, 111, 220, 146, 218, 39, 76, 114, 75, 3, 207, 55, 106, 29, 136, 227, 92, 135, 62, 190, 23, 62, 67, 2, 17, 0, 0, 0, 14, 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