Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3344fac1752d2f172f1d99ebb37fed3d8165ca301c8081a43ad691876d264ecb

Tx prefix hash: 5f8e90ceef57a8520c4e7f9cfcf62b8dea65e2a0b31167cfe5d6bc3282a800ee
Tx public key: 94d613c6cb0c81661252c431b8f21c7ca3e59fc2836b34b4df33185c28645a18
Timestamp: 1701658650 Timestamp [UCT]: 2023-12-04 02:57:30 Age [y:d:h:m:s]: 01:172:06:50:33
Block: 905486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384334 RingCT/type: yes/0
Extra: 0194d613c6cb0c81661252c431b8f21c7ca3e59fc2836b34b4df33185c28645a18021100000004e08532b6000000000000000000

1 output(s) for total of 0.613407345000 dcy

stealth address amount amount idx
00: e25fba165726998f43d21de30afce08985de2c59bff305c4df759201a487b70a 0.613407345000 1362375 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": 905496, "vin": [ { "gen": { "height": 905486 } } ], "vout": [ { "amount": 613407345, "target": { "key": "e25fba165726998f43d21de30afce08985de2c59bff305c4df759201a487b70a" } } ], "extra": [ 1, 148, 214, 19, 198, 203, 12, 129, 102, 18, 82, 196, 49, 184, 242, 28, 124, 163, 229, 159, 194, 131, 107, 52, 180, 223, 51, 24, 92, 40, 100, 90, 24, 2, 17, 0, 0, 0, 4, 224, 133, 50, 182, 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