Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66a0f9415d1d4d557463ca5b5841966c92d1f882748e2c3e20f6de5f68841149

Tx prefix hash: 883bc1e88d23f474864cbe6277af4464289054a47fee93c370cb885df397c313
Tx public key: 652a98b9b919cea3d98ab35890677d85f6da839850e789495fbf3b4c0df10a1b
Timestamp: 1701207461 Timestamp [UCT]: 2023-11-28 21:37:41 Age [y:d:h:m:s]: 01:087:19:03:25
Block: 901765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323857 RingCT/type: yes/0
Extra: 01652a98b9b919cea3d98ab35890677d85f6da839850e789495fbf3b4c0df10a1b02110000000233af99f4000000000000000000

1 output(s) for total of 0.631070959000 dcy

stealth address amount amount idx
00: ea39a5678e6cd3a9fbccad1a5a5ec72b87ba0f699da1c0e60865d47e60b667f5 0.631070959000 1358354 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": 901775, "vin": [ { "gen": { "height": 901765 } } ], "vout": [ { "amount": 631070959, "target": { "key": "ea39a5678e6cd3a9fbccad1a5a5ec72b87ba0f699da1c0e60865d47e60b667f5" } } ], "extra": [ 1, 101, 42, 152, 185, 185, 25, 206, 163, 217, 138, 179, 88, 144, 103, 125, 133, 246, 218, 131, 152, 80, 231, 137, 73, 95, 191, 59, 76, 13, 241, 10, 27, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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