Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: feb4136d6f567fa3ba46e2433e63ca16080f58c1e14ce6fcc46107c3b357b683

Tx prefix hash: 744a4a3e1fc686254fdaae98beda919641b7946e11e5dc9f7e245487ff231acd
Tx public key: 57ad66de24cfa32a3e940c94c169c2a28ef00923ce1d4dc43a1a3140405a773d
Timestamp: 1731905035 Timestamp [UCT]: 2024-11-18 04:43:55 Age [y:d:h:m:s]: 00:130:19:08:31
Block: 1156162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93292 RingCT/type: yes/0
Extra: 0157ad66de24cfa32a3e940c94c169c2a28ef00923ce1d4dc43a1a3140405a773d021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9aaa274f12052a31f32d99aa76ad88e7c11ba7dd0d52887429cbfe4195fb5335 0.600000000000 1641785 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": 1156172, "vin": [ { "gen": { "height": 1156162 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9aaa274f12052a31f32d99aa76ad88e7c11ba7dd0d52887429cbfe4195fb5335" } } ], "extra": [ 1, 87, 173, 102, 222, 36, 207, 163, 42, 62, 148, 12, 148, 193, 105, 194, 162, 142, 240, 9, 35, 206, 29, 77, 196, 58, 26, 49, 64, 64, 90, 119, 61, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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