Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44db92c3fdc2721af3eaacfb42bc9f053c29726aadb0fd1404505068252e4bc0

Tx prefix hash: fc4fbfbebfac7cb346f126ec17206705a5e5b64d4027a8506ad3769cdd817677
Tx public key: c332f8112ae9dcd50f1e944ae987f02df9acde20b55edfe7027cdbe2b9fec7eb
Timestamp: 1706977825 Timestamp [UCT]: 2024-02-03 16:30:25 Age [y:d:h:m:s]: 01:074:16:03:43
Block: 949577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314447 RingCT/type: yes/0
Extra: 01c332f8112ae9dcd50f1e944ae987f02df9acde20b55edfe7027cdbe2b9fec7eb02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8831dfc5b72858b5fd0d56f5b0f3f71fdccc28935cc0edb8b24b16e3d7868e2 0.600000000000 1408107 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": 949587, "vin": [ { "gen": { "height": 949577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8831dfc5b72858b5fd0d56f5b0f3f71fdccc28935cc0edb8b24b16e3d7868e2" } } ], "extra": [ 1, 195, 50, 248, 17, 42, 233, 220, 213, 15, 30, 148, 74, 233, 135, 240, 45, 249, 172, 222, 32, 181, 94, 223, 231, 2, 124, 219, 226, 185, 254, 199, 235, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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