Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfbc6fda8b7ef4883abdb22ed63f4bbecb9f58e482f3f0d83c8f6ea0572b3cc7

Tx prefix hash: e975026411a6f9649ffa473b3340bc00b4e1de118be5458ddc03e58d3c9b52d7
Tx public key: 8a5701978c8adbb00975b48738ed1f50416a378232fe48a0f8e77c8f5f376f1d
Timestamp: 1648339792 Timestamp [UCT]: 2022-03-27 00:09:52 Age [y:d:h:m:s]: 02:249:10:21:02
Block: 467110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 697813 RingCT/type: yes/0
Extra: 018a5701978c8adbb00975b48738ed1f50416a378232fe48a0f8e77c8f5f376f1d0211000000152e6b1fd5000000000000000000

1 output(s) for total of 17.389152240000 dcy

stealth address amount amount idx
00: 0d51a59def8c3d9c8fcc5fd76e8f99623c2ed2ca2c6b772e76633d6392f3220c 17.389152240000 885555 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": 467120, "vin": [ { "gen": { "height": 467110 } } ], "vout": [ { "amount": 17389152240, "target": { "key": "0d51a59def8c3d9c8fcc5fd76e8f99623c2ed2ca2c6b772e76633d6392f3220c" } } ], "extra": [ 1, 138, 87, 1, 151, 140, 138, 219, 176, 9, 117, 180, 135, 56, 237, 31, 80, 65, 106, 55, 130, 50, 254, 72, 160, 248, 231, 124, 143, 95, 55, 111, 29, 2, 17, 0, 0, 0, 21, 46, 107, 31, 213, 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