Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d443351e2742138459aa0e534f06713848feff7a0f9520556c80553342a2068

Tx prefix hash: b9e600b80660664604515f90b4e61e224efd82d9be32250e5a6bfcadb1c7fd96
Tx public key: 0cac86207bbbcd59cf8ad571d77603e64ae7d1a54ab0a7dcc1d0ad59e4d664c8
Timestamp: 1702962901 Timestamp [UCT]: 2023-12-19 05:15:01 Age [y:d:h:m:s]: 01:153:21:40:17
Block: 916320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371151 RingCT/type: yes/0
Extra: 010cac86207bbbcd59cf8ad571d77603e64ae7d1a54ab0a7dcc1d0ad59e4d664c8021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.605780000000 dcy

stealth address amount amount idx
00: b706ebe572643346d0f9f91784e3bce7fe02dfca2019a194bdda20b3344508a2 0.605780000000 1373808 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": 916330, "vin": [ { "gen": { "height": 916320 } } ], "vout": [ { "amount": 605780000, "target": { "key": "b706ebe572643346d0f9f91784e3bce7fe02dfca2019a194bdda20b3344508a2" } } ], "extra": [ 1, 12, 172, 134, 32, 123, 187, 205, 89, 207, 138, 213, 113, 215, 118, 3, 230, 74, 231, 209, 165, 74, 176, 167, 220, 193, 208, 173, 89, 228, 214, 100, 200, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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