Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 153d1824a298c441c012f33f5fab8bd6c29da51af0c3d4e39c3b674f6c5e19f5

Tx prefix hash: 311a91b3381f86ddc8d5acd8a0193beb2325679b04351cb3f24a328082fde3e0
Tx public key: fbd59f422e2c2fbebfbb1f7a59a2c138af57adf37f13207d238089dd6b9b467f
Timestamp: 1578893976 Timestamp [UCT]: 2020-01-13 05:39:36 Age [y:d:h:m:s]: 04:352:11:48:43
Block: 44396 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1141475 RingCT/type: yes/0
Extra: 01fbd59f422e2c2fbebfbb1f7a59a2c138af57adf37f13207d238089dd6b9b467f02110000000f4ac5aa02000000000000000000

1 output(s) for total of 437.419826045000 dcy

stealth address amount amount idx
00: 2afff4b5db5d9eb9013265954a9662ba3cdd5f2136d5d39b248526689e74ecdc 437.419826045000 80774 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": 44406, "vin": [ { "gen": { "height": 44396 } } ], "vout": [ { "amount": 437419826045, "target": { "key": "2afff4b5db5d9eb9013265954a9662ba3cdd5f2136d5d39b248526689e74ecdc" } } ], "extra": [ 1, 251, 213, 159, 66, 46, 44, 47, 190, 191, 187, 31, 122, 89, 162, 193, 56, 175, 87, 173, 243, 127, 19, 32, 125, 35, 128, 137, 221, 107, 155, 70, 127, 2, 17, 0, 0, 0, 15, 74, 197, 170, 2, 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