Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 027c38bd497f725b29c0a60e83e211f13f70e8f26866b5bb77e2c153fbdeb72b

Tx prefix hash: a7769a9c176a7abe9aebbd328865627e6af85ba08f72b277a03de6e031e57719
Tx public key: 44e4f779616de19fd35a2398c9c78a5a97ce7893e1fd114a5eed38e31db171fc
Timestamp: 1728290354 Timestamp [UCT]: 2024-10-07 08:39:14 Age [y:d:h:m:s]: 00:052:01:03:46
Block: 1126288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37187 RingCT/type: yes/0
Extra: 0144e4f779616de19fd35a2398c9c78a5a97ce7893e1fd114a5eed38e31db171fc021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9e69cd8015bd3d76b4dffb48fa6da897105f0e1b8341a4fed36b458c51c9e06 0.600000000000 1609077 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": 1126298, "vin": [ { "gen": { "height": 1126288 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9e69cd8015bd3d76b4dffb48fa6da897105f0e1b8341a4fed36b458c51c9e06" } } ], "extra": [ 1, 68, 228, 247, 121, 97, 109, 225, 159, 211, 90, 35, 152, 201, 199, 138, 90, 151, 206, 120, 147, 225, 253, 17, 74, 94, 237, 56, 227, 29, 177, 113, 252, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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