Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdc214bd751c9cec49444b5d1b85fc6b1929d4122a3351db5b8c42af42b41389

Tx prefix hash: 64fba08cc7c0db77ef7833fcafa608efe0e0542f529ac1ee2298db3b9ab281bd
Tx public key: 3168ed1a2ce896f7db6909fcd7e8870aa7998d90c7a3af9ebbe7343cea324521
Timestamp: 1624463731 Timestamp [UCT]: 2021-06-23 15:55:31 Age [y:d:h:m:s]: 03:189:09:00:41
Block: 282964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 902410 RingCT/type: yes/0
Extra: 013168ed1a2ce896f7db6909fcd7e8870aa7998d90c7a3af9ebbe7343cea324521021100000024bcea621d000000000000000000

1 output(s) for total of 70.863617574000 dcy

stealth address amount amount idx
00: 754ccfb084acf611011a394264d21fa7dee6d241fe054b614e614bae7186fb9a 70.863617574000 592543 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": 282974, "vin": [ { "gen": { "height": 282964 } } ], "vout": [ { "amount": 70863617574, "target": { "key": "754ccfb084acf611011a394264d21fa7dee6d241fe054b614e614bae7186fb9a" } } ], "extra": [ 1, 49, 104, 237, 26, 44, 232, 150, 247, 219, 105, 9, 252, 215, 232, 135, 10, 167, 153, 141, 144, 199, 163, 175, 158, 187, 231, 52, 60, 234, 50, 69, 33, 2, 17, 0, 0, 0, 36, 188, 234, 98, 29, 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