Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0312c0de44ae48ce4533eb85fe5f70118ec322129bf0dd651ea7547f06f47f15

Tx prefix hash: 212ea94817fa1c7f884cc46df64f2e263ff7835fd2b49f726bae8cbfe0cdaf67
Tx public key: b5456891a387c26bd7b9d44c4cfc2f03f533d591350b79cea85ff2e1de6d7cfb
Timestamp: 1703547995 Timestamp [UCT]: 2023-12-25 23:46:35 Age [y:d:h:m:s]: 01:100:02:21:22
Block: 921160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332647 RingCT/type: yes/0
Extra: 01b5456891a387c26bd7b9d44c4cfc2f03f533d591350b79cea85ff2e1de6d7cfb021100000003ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c5cffbae1aa0e080276edd1c2fff6bc57a800494f7ddf6bbbc0275636cb8d63 0.600000000000 1378844 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": 921170, "vin": [ { "gen": { "height": 921160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c5cffbae1aa0e080276edd1c2fff6bc57a800494f7ddf6bbbc0275636cb8d63" } } ], "extra": [ 1, 181, 69, 104, 145, 163, 135, 194, 107, 215, 185, 212, 76, 76, 252, 47, 3, 245, 51, 213, 145, 53, 11, 121, 206, 168, 95, 242, 225, 222, 109, 124, 251, 2, 17, 0, 0, 0, 3, 173, 86, 148, 172, 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