Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c80e5c4992bbeef8b462af6611a261ecb933ca9a440a0188c44db7e965de769c

Tx prefix hash: 06103b2653e5d58732a275a449d3384ce5cd785beb1f5ac6a9428d75b3fd2d3b
Tx public key: 9e117fa3bd8632ce2ea7c469d2a30e6e451343796dded1c64e913293df5ab1be
Timestamp: 1704330137 Timestamp [UCT]: 2024-01-04 01:02:17 Age [y:d:h:m:s]: 01:307:00:57:19
Block: 927656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478229 RingCT/type: yes/0
Extra: 019e117fa3bd8632ce2ea7c469d2a30e6e451343796dded1c64e913293df5ab1be021100000001e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a7a87979a7e634be5d48908a124785e15658c92d54e6df08096e4b42752df87 0.600000000000 1385492 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": 927666, "vin": [ { "gen": { "height": 927656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a7a87979a7e634be5d48908a124785e15658c92d54e6df08096e4b42752df87" } } ], "extra": [ 1, 158, 17, 127, 163, 189, 134, 50, 206, 46, 167, 196, 105, 210, 163, 14, 110, 69, 19, 67, 121, 109, 222, 209, 198, 78, 145, 50, 147, 223, 90, 177, 190, 2, 17, 0, 0, 0, 1, 228, 187, 107, 131, 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