Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a58ccfa9d3d31a05897032d58edb54075aa918e2b215d6b904919ceb7aa35fc

Tx prefix hash: 5e5ae6e7a5744181e7dd7b889cd199927db472603b2c1f2be1c33bbab4c60202
Tx public key: f8c317fdf65bbff2c5791db6b6719a1d3b5e4092404f02efc6ca210a7780cdd9
Timestamp: 1648523647 Timestamp [UCT]: 2022-03-29 03:14:07 Age [y:d:h:m:s]: 02:250:16:23:58
Block: 468641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 698702 RingCT/type: yes/0
Extra: 01f8c317fdf65bbff2c5791db6b6719a1d3b5e4092404f02efc6ca210a7780cdd902110000000ed3fcec30000000000000000000

1 output(s) for total of 17.186920826000 dcy

stealth address amount amount idx
00: f6b8544bbe8847c219aeb553dcce5c3c98ceee47f5ab3ce3f2309a76de62f4a0 17.186920826000 887397 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": 468651, "vin": [ { "gen": { "height": 468641 } } ], "vout": [ { "amount": 17186920826, "target": { "key": "f6b8544bbe8847c219aeb553dcce5c3c98ceee47f5ab3ce3f2309a76de62f4a0" } } ], "extra": [ 1, 248, 195, 23, 253, 246, 91, 191, 242, 197, 121, 29, 182, 182, 113, 154, 29, 59, 94, 64, 146, 64, 79, 2, 239, 198, 202, 33, 10, 119, 128, 205, 217, 2, 17, 0, 0, 0, 14, 211, 252, 236, 48, 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