Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ffed1ad76d03606413c293d71b830e801ef884846242c394f28fbc5b6ff25a4

Tx prefix hash: 4e0100879bf55a73fe5c65b91cf39adc304f2704d2fac63ce8da40eb8c09ca46
Tx public key: bc59a964b1bd1183112c53310897126e644f2ea4abd0875b459274c9e0c7ac51
Timestamp: 1621582028 Timestamp [UCT]: 2021-05-21 07:27:08 Age [y:d:h:m:s]: 04:094:19:27:45
Block: 264454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1087951 RingCT/type: yes/0
Extra: 01bc59a964b1bd1183112c53310897126e644f2ea4abd0875b459274c9e0c7ac5102110000000efdc4fdba000000000000000000

1 output(s) for total of 81.612120061000 dcy

stealth address amount amount idx
00: 1eace44bdb84235d52ce7b671f20a7c6c40850d1b8c7be9c56da64a4e094c404 81.612120061000 556084 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": 264464, "vin": [ { "gen": { "height": 264454 } } ], "vout": [ { "amount": 81612120061, "target": { "key": "1eace44bdb84235d52ce7b671f20a7c6c40850d1b8c7be9c56da64a4e094c404" } } ], "extra": [ 1, 188, 89, 169, 100, 177, 189, 17, 131, 17, 44, 83, 49, 8, 151, 18, 110, 100, 79, 46, 164, 171, 208, 135, 91, 69, 146, 116, 201, 224, 199, 172, 81, 2, 17, 0, 0, 0, 14, 253, 196, 253, 186, 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