Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8543bc42c484b831a722be288af9f3705ed8b5162a6ce7771bd49a2c78eada1

Tx prefix hash: 085a340144ea7c3a9baab9fb167f2fdfa0aea22fa7846944bc3a9fe7c54be1ce
Tx public key: 064fe862322e33796df2d3d7c03e0724b73fbaa924a41a8ba339f2097cea0f4f
Timestamp: 1745971638 Timestamp [UCT]: 2025-04-30 00:07:18 Age [y:d:h:m:s]: 00:023:20:47:13
Block: 1272360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17074 RingCT/type: yes/0
Extra: 01064fe862322e33796df2d3d7c03e0724b73fbaa924a41a8ba339f2097cea0f4f02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ebfa0b7ba53cc0e67157509084f0c3681068b781f10cee1973864b63ee423aeb 0.600000000000 1759635 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": 1272370, "vin": [ { "gen": { "height": 1272360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ebfa0b7ba53cc0e67157509084f0c3681068b781f10cee1973864b63ee423aeb" } } ], "extra": [ 1, 6, 79, 232, 98, 50, 46, 51, 121, 109, 242, 211, 215, 192, 62, 7, 36, 183, 63, 186, 169, 36, 164, 26, 139, 163, 57, 242, 9, 124, 234, 15, 79, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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