Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3579fc5b49dbf6c9e0b037e47f2c7660456d457d08fa0157118f0e489976984

Tx prefix hash: b3e376facef1df0b31a749c2523a98d09f236ee8b3f8ad25ae197f5c1728318a
Tx public key: 5337b38df2728f3e3317ad351942b105d1b55c253df237fe65def4c18d4cfbc9
Timestamp: 1704847247 Timestamp [UCT]: 2024-01-10 00:40:47 Age [y:d:h:m:s]: 01:081:13:02:48
Block: 931919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319378 RingCT/type: yes/0
Extra: 015337b38df2728f3e3317ad351942b105d1b55c253df237fe65def4c18d4cfbc902110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 869d2011d0cec57321c21a770f5621c8656227e050aa03eafcaea525fdb0bcfe 0.600000000000 1389825 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": 931929, "vin": [ { "gen": { "height": 931919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "869d2011d0cec57321c21a770f5621c8656227e050aa03eafcaea525fdb0bcfe" } } ], "extra": [ 1, 83, 55, 179, 141, 242, 114, 143, 62, 51, 23, 173, 53, 25, 66, 177, 5, 209, 181, 92, 37, 61, 242, 55, 254, 101, 222, 244, 193, 141, 76, 251, 201, 2, 17, 0, 0, 0, 7, 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