Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cdb0fbde65aa42f9a216e26cf568bc08f0f73147e49c329317c229ca95c213f

Tx prefix hash: 58cb3629e9af67226da1b41fd5fe0680872c73d435493d56880b37effbaba40f
Tx public key: 3f14d5f9830947de3c2126e59bcb623a2a76f46fe39fb154228cf830eda7db23
Timestamp: 1686854279 Timestamp [UCT]: 2023-06-15 18:37:59 Age [y:d:h:m:s]: 01:319:17:42:27
Block: 783007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 489715 RingCT/type: yes/0
Extra: 013f14d5f9830947de3c2126e59bcb623a2a76f46fe39fb154228cf830eda7db23021100000002e6d27f9c000000000000000000

1 output(s) for total of 1.561611225000 dcy

stealth address amount amount idx
00: b7ad06e0ca39c0f1b7b140d5ae2e35e11641aaa80b095906a8164f9fe4ac8d75 1.561611225000 1232844 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": 783017, "vin": [ { "gen": { "height": 783007 } } ], "vout": [ { "amount": 1561611225, "target": { "key": "b7ad06e0ca39c0f1b7b140d5ae2e35e11641aaa80b095906a8164f9fe4ac8d75" } } ], "extra": [ 1, 63, 20, 213, 249, 131, 9, 71, 222, 60, 33, 38, 229, 155, 203, 98, 58, 42, 118, 244, 111, 227, 159, 177, 84, 34, 140, 248, 48, 237, 167, 219, 35, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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