Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1541e2b529bab52bb7d86d4890e0abcaa8bc1412b84ebb94bf818c71437402ed

Tx prefix hash: 1301faac45699bb20645efc30342d99e98ae5fd97ef9e741b04b3fdb6a690875
Tx public key: 1c869013159dce2b396c809cffa3d3d804c876fcab5888e2fb674cd6ce37fbde
Timestamp: 1709444289 Timestamp [UCT]: 2024-03-03 05:38:09 Age [y:d:h:m:s]: 01:250:16:11:30
Block: 970047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437877 RingCT/type: yes/0
Extra: 011c869013159dce2b396c809cffa3d3d804c876fcab5888e2fb674cd6ce37fbde02110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5be630a814677d2ac28968783c235d886d0cfac5cfa4ef5a389975aa85b37531 0.600000000000 1429896 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": 970057, "vin": [ { "gen": { "height": 970047 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5be630a814677d2ac28968783c235d886d0cfac5cfa4ef5a389975aa85b37531" } } ], "extra": [ 1, 28, 134, 144, 19, 21, 157, 206, 43, 57, 108, 128, 156, 255, 163, 211, 216, 4, 200, 118, 252, 171, 88, 136, 226, 251, 103, 76, 214, 206, 55, 251, 222, 2, 17, 0, 0, 0, 11, 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