Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7e3bbcd51ff2cc0d2821708a712a315bb2160d8b698eca08fcf5c54de2b5c0e

Tx prefix hash: cbba9373d500e37b4e1f3f3bd07eb8465b37fe20ead94c940f8f416ad7171c6f
Tx public key: b61be0d307507ad71e399b7075a241d9d79bff5ec75f94c86a2631a3964c247f
Timestamp: 1734438928 Timestamp [UCT]: 2024-12-17 12:35:28 Age [y:d:h:m:s]: 00:104:21:54:48
Block: 1177172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74739 RingCT/type: yes/0
Extra: 01b61be0d307507ad71e399b7075a241d9d79bff5ec75f94c86a2631a3964c247f021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 554055bf4c57b7feec2eafac7978485022f4bbf70d71179734b1dbf107234f06 0.600000000000 1663537 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": 1177182, "vin": [ { "gen": { "height": 1177172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "554055bf4c57b7feec2eafac7978485022f4bbf70d71179734b1dbf107234f06" } } ], "extra": [ 1, 182, 27, 224, 211, 7, 80, 122, 215, 30, 57, 155, 112, 117, 162, 65, 217, 215, 155, 255, 94, 199, 95, 148, 200, 106, 38, 49, 163, 150, 76, 36, 127, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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