Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 382ebccee7a7b3fd877e5fc12a4cf6bcfcb682000c53ca790ec55fa35b5b3730

Tx prefix hash: e444c0726cda2c6cf3a8ebc3a2e15511703424024e71735ddd896fcab29a3e12
Tx public key: 50d28741cc11106804e57bdddafa80a7d376f27179d83b44fcd267ae022ce968
Timestamp: 1649832416 Timestamp [UCT]: 2022-04-13 06:46:56 Age [y:d:h:m:s]: 02:334:16:49:27
Block: 479132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 758889 RingCT/type: yes/0
Extra: 0150d28741cc11106804e57bdddafa80a7d376f27179d83b44fcd267ae022ce9680211000000014da16a3a000000000000000000

1 output(s) for total of 15.864888454000 dcy

stealth address amount amount idx
00: cf8b0640dc9635fa3296427c8c9f7da5d082beb03688e45d3a7e6224f7244cbb 15.864888454000 899969 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": 479142, "vin": [ { "gen": { "height": 479132 } } ], "vout": [ { "amount": 15864888454, "target": { "key": "cf8b0640dc9635fa3296427c8c9f7da5d082beb03688e45d3a7e6224f7244cbb" } } ], "extra": [ 1, 80, 210, 135, 65, 204, 17, 16, 104, 4, 229, 123, 221, 218, 250, 128, 167, 211, 118, 242, 113, 121, 216, 59, 68, 252, 210, 103, 174, 2, 44, 233, 104, 2, 17, 0, 0, 0, 1, 77, 161, 106, 58, 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