Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19c7359c1b13254790971a6ecbe0a5ff7b44362ff6fd42a00326956f60166491

Tx prefix hash: d1f3c234b631635540915d1b06b22b592a899f4c963cb5ad7651c90ed028b02d
Tx public key: 83b710dc86d4676f34a8d1f87ef27017df1e2258458049f97031ab9b3c1aedc7
Timestamp: 1673135431 Timestamp [UCT]: 2023-01-07 23:50:31 Age [y:d:h:m:s]: 02:143:05:02:26
Block: 669887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 624077 RingCT/type: yes/0
Extra: 0183b710dc86d4676f34a8d1f87ef27017df1e2258458049f97031ab9b3c1aedc702110000000752542ceb000000000000000000

1 output(s) for total of 3.701572356000 dcy

stealth address amount amount idx
00: 437e22437d7cc07ac22cd89acb21dbc0da809062b769df112dc01a90045f5cf0 3.701572356000 1111254 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": 669897, "vin": [ { "gen": { "height": 669887 } } ], "vout": [ { "amount": 3701572356, "target": { "key": "437e22437d7cc07ac22cd89acb21dbc0da809062b769df112dc01a90045f5cf0" } } ], "extra": [ 1, 131, 183, 16, 220, 134, 212, 103, 111, 52, 168, 209, 248, 126, 242, 112, 23, 223, 30, 34, 88, 69, 128, 73, 249, 112, 49, 171, 155, 60, 26, 237, 199, 2, 17, 0, 0, 0, 7, 82, 84, 44, 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