Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5be273a39b579ad65f2ceaff252352acf0a466f8e7fd07de892c88f1d2cc617f

Tx prefix hash: 881d2591cc98426d125c2e72a1253f5a3961278910a3e4256dff57b954c921a3
Tx public key: d876f07fb77669a5dcdb03c01e4dec42c116acdfa3ae410a54c2f3f0275c6fd7
Timestamp: 1688377300 Timestamp [UCT]: 2023-07-03 09:41:40 Age [y:d:h:m:s]: 01:316:07:52:43
Block: 795649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 487250 RingCT/type: yes/0
Extra: 01d876f07fb77669a5dcdb03c01e4dec42c116acdfa3ae410a54c2f3f0275c6fd702110000000233af99f4000000000000000000

1 output(s) for total of 1.418027684000 dcy

stealth address amount amount idx
00: 16b6a91a13df92fd6afd04801f1c18468863a502dbf4a50813b75f518b19d72b 1.418027684000 1246470 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": 795659, "vin": [ { "gen": { "height": 795649 } } ], "vout": [ { "amount": 1418027684, "target": { "key": "16b6a91a13df92fd6afd04801f1c18468863a502dbf4a50813b75f518b19d72b" } } ], "extra": [ 1, 216, 118, 240, 127, 183, 118, 105, 165, 220, 219, 3, 192, 30, 77, 236, 66, 193, 22, 172, 223, 163, 174, 65, 10, 84, 194, 243, 240, 39, 92, 111, 215, 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