Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b3d9e586645da92d1247cb798c2ccd06efaa5f5a447f597146f0176f69d4518

Tx prefix hash: 96205beb1bb017a6aa6abfd5160947ae49474230b1ab1351c82cfba04316d08f
Tx public key: febde2b07ae42a19878c5fe9898ca9cd6aff81ef36df1d77cd8d168731ae64fb
Timestamp: 1580264633 Timestamp [UCT]: 2020-01-29 02:23:53 Age [y:d:h:m:s]: 04:332:18:50:32
Block: 54409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128726 RingCT/type: yes/0
Extra: 01febde2b07ae42a19878c5fe9898ca9cd6aff81ef36df1d77cd8d168731ae64fb021100000002dcee4b4d000000000000000000

1 output(s) for total of 405.248320151000 dcy

stealth address amount amount idx
00: 38920e31cf48a0eb4c240e22fc8f9c1f208d9dd3f3755b85395462d993ae61f8 405.248320151000 100784 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": 54419, "vin": [ { "gen": { "height": 54409 } } ], "vout": [ { "amount": 405248320151, "target": { "key": "38920e31cf48a0eb4c240e22fc8f9c1f208d9dd3f3755b85395462d993ae61f8" } } ], "extra": [ 1, 254, 189, 226, 176, 122, 228, 42, 25, 135, 140, 95, 233, 137, 140, 169, 205, 106, 255, 129, 239, 54, 223, 29, 119, 205, 141, 22, 135, 49, 174, 100, 251, 2, 17, 0, 0, 0, 2, 220, 238, 75, 77, 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