Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 938792444d88226ff83c819f2e7a2a57d3b8e8378a34661e0c37189ae473560a

Tx prefix hash: c642b5a32623a2cf18da8eaf67064cdc954a459d8ef936d6a951331d0932fb4b
Tx public key: 791b6d44ec8440e1b31c16a9e304001f19e57c8bc0159daa1a2d3b2285376123
Timestamp: 1700918471 Timestamp [UCT]: 2023-11-25 13:21:11 Age [y:d:h:m:s]: 01:349:13:28:32
Block: 899367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 508703 RingCT/type: yes/0
Extra: 01791b6d44ec8440e1b31c16a9e304001f19e57c8bc0159daa1a2d3b228537612302110000000875e3f0e9000000000000000000

1 output(s) for total of 0.642722892000 dcy

stealth address amount amount idx
00: 4bc6929e850d91c85d562813000e5960264941f120f889865bdc0ca543396034 0.642722892000 1355820 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": 899377, "vin": [ { "gen": { "height": 899367 } } ], "vout": [ { "amount": 642722892, "target": { "key": "4bc6929e850d91c85d562813000e5960264941f120f889865bdc0ca543396034" } } ], "extra": [ 1, 121, 27, 109, 68, 236, 132, 64, 225, 179, 28, 22, 169, 227, 4, 0, 31, 25, 229, 124, 139, 192, 21, 157, 170, 26, 45, 59, 34, 133, 55, 97, 35, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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