Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d316344a994ea5cb36b581e5ff5076a29e9053ebfa42ba91b99416763dc1d8f9

Tx prefix hash: 0ff2c8ac0506919aa253d841bcac32c9d8e80f0473a89ccc65f42d685c652416
Tx public key: 2ee1f4ce9325d28f385e29b75ffaec32bf7a55c680fa7a6cc1a2ef6541181148
Timestamp: 1722297078 Timestamp [UCT]: 2024-07-29 23:51:18 Age [y:d:h:m:s]: 00:230:03:11:54
Block: 1076591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164388 RingCT/type: yes/0
Extra: 012ee1f4ce9325d28f385e29b75ffaec32bf7a55c680fa7a6cc1a2ef6541181148021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bb7f700b5c996cff5da60274f9edc9f307f956cd47e5ea2c45d470e15603608 0.600000000000 1549130 of 15

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": 1076601, "vin": [ { "gen": { "height": 1076591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bb7f700b5c996cff5da60274f9edc9f307f956cd47e5ea2c45d470e15603608" } } ], "extra": [ 1, 46, 225, 244, 206, 147, 37, 210, 143, 56, 94, 41, 183, 95, 250, 236, 50, 191, 122, 85, 198, 128, 250, 122, 108, 193, 162, 239, 101, 65, 24, 17, 72, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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