Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d0b7c904383fcb997b7ea817af231e62de83e6471717888fa0ecfe5ed1fb492

Tx prefix hash: 9027f68bfbe62d164a29fd45fb4ed732f70d00cd5e034032529f34f8c57b10e2
Tx public key: e690fd6f0fcffd5bff78948f19c06a05b93f4fec6f61a8da49c789049557abff
Timestamp: 1707650493 Timestamp [UCT]: 2024-02-11 11:21:33 Age [y:d:h:m:s]: 01:049:15:46:25
Block: 955166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296523 RingCT/type: yes/0
Extra: 01e690fd6f0fcffd5bff78948f19c06a05b93f4fec6f61a8da49c789049557abff02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73c2b27790f15d3b582b7de2951ee5994d97f2149c9c4e1cd2b60cc7458b47e3 0.600000000000 1414452 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": 955176, "vin": [ { "gen": { "height": 955166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73c2b27790f15d3b582b7de2951ee5994d97f2149c9c4e1cd2b60cc7458b47e3" } } ], "extra": [ 1, 230, 144, 253, 111, 15, 207, 253, 91, 255, 120, 148, 143, 25, 192, 106, 5, 185, 63, 79, 236, 111, 97, 168, 218, 73, 199, 137, 4, 149, 87, 171, 255, 2, 17, 0, 0, 0, 1, 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