Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 996bbc3d8d49e8d3f7cbfc83239bd530c2dbf2138d76cca241b75418588aa617

Tx prefix hash: af39e41b6fac5f35894f2669be50ad5203263f79375d9ca62b779cd31fcb5eeb
Tx public key: cbb3e3b1a864814370f4dee73d01f3ee03dc69aa0bb9e9440ebec3b6fef81154
Timestamp: 1636768454 Timestamp [UCT]: 2021-11-13 01:54:14 Age [y:d:h:m:s]: 03:004:15:40:42
Block: 373191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 781909 RingCT/type: yes/0
Extra: 01cbb3e3b1a864814370f4dee73d01f3ee03dc69aa0bb9e9440ebec3b6fef8115402110000000906faf294000000000000000000

1 output(s) for total of 35.601742189000 dcy

stealth address amount amount idx
00: cc0195022c0de9a1df96c5f9d7b4d512583c1541f9ce6750b04f0df0a881e0dc 35.601742189000 755749 of 0

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": 373201, "vin": [ { "gen": { "height": 373191 } } ], "vout": [ { "amount": 35601742189, "target": { "key": "cc0195022c0de9a1df96c5f9d7b4d512583c1541f9ce6750b04f0df0a881e0dc" } } ], "extra": [ 1, 203, 179, 227, 177, 168, 100, 129, 67, 112, 244, 222, 231, 61, 1, 243, 238, 3, 220, 105, 170, 11, 185, 233, 68, 14, 190, 195, 182, 254, 248, 17, 84, 2, 17, 0, 0, 0, 9, 6, 250, 242, 148, 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