Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d03dfac919ba23276170bb740a016d0f84b996622fb963df6c302cb9107519f5

Tx prefix hash: fda00bf5cc3a613d190b13ded77bb4dbb23f6009babe86ad122ad9ffa23a7cdc
Tx public key: 09b35bfd84b627f7488ce2eff1a244a90e28c45c145ac2a649125bff05d657a4
Timestamp: 1577906868 Timestamp [UCT]: 2020-01-01 19:27:48 Age [y:d:h:m:s]: 04:140:13:06:53
Block: 36555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 989449 RingCT/type: yes/0
Extra: 0109b35bfd84b627f7488ce2eff1a244a90e28c45c145ac2a649125bff05d657a4021100000073c3a1a09f000000000000000000

1 output(s) for total of 464.406643764000 dcy

stealth address amount amount idx
00: 7f20ab3f848b1657787060958d644f8fd5f9f0ded7bfdf45a604df562b5e5efc 464.406643764000 61948 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": 36565, "vin": [ { "gen": { "height": 36555 } } ], "vout": [ { "amount": 464406643764, "target": { "key": "7f20ab3f848b1657787060958d644f8fd5f9f0ded7bfdf45a604df562b5e5efc" } } ], "extra": [ 1, 9, 179, 91, 253, 132, 182, 39, 247, 72, 140, 226, 239, 241, 162, 68, 169, 14, 40, 196, 92, 20, 90, 194, 166, 73, 18, 91, 255, 5, 214, 87, 164, 2, 17, 0, 0, 0, 115, 195, 161, 160, 159, 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