Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e127056fc7b3de4c8c82f779c9910fae6666c33ef7acc3914003e92e21082823

Tx prefix hash: 5f9ee30b35f18c611b26778478bf1f032ffd9b2ec2901d21f5b5f16851619bcc
Tx public key: 485cb4c28cf112109a17b2baac28bd00dc717c95b9a3945c7e2b75cc28724473
Timestamp: 1742908183 Timestamp [UCT]: 2025-03-25 13:09:43 Age [y:d:h:m:s]: 00:235:13:18:27
Block: 1246997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166082 RingCT/type: yes/0
Extra: 01485cb4c28cf112109a17b2baac28bd00dc717c95b9a3945c7e2b75cc28724473021100000003c6740958000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f49181e2f4709205a5633e351c226a2d3e47c580116d02a66c7fd7bc3d4b94d4 0.600000000000 1733998 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": 1247007, "vin": [ { "gen": { "height": 1246997 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f49181e2f4709205a5633e351c226a2d3e47c580116d02a66c7fd7bc3d4b94d4" } } ], "extra": [ 1, 72, 92, 180, 194, 140, 241, 18, 16, 154, 23, 178, 186, 172, 40, 189, 0, 220, 113, 124, 149, 185, 163, 148, 92, 126, 43, 117, 204, 40, 114, 68, 115, 2, 17, 0, 0, 0, 3, 198, 116, 9, 88, 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