Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a22bc59820d624ae8f7946f0c3b52bdae211a83ccb6e23807a99ba3db84b44a

Tx prefix hash: 4dcb932fdb4252b78d6d7b8d199d4c546cd76f13ccd1591362d3c830972529b2
Tx public key: 41fbf0e70ac106f0eb0a7cf97e29e05282a0a6573836a1f8355cc52c92456c62
Timestamp: 1742829763 Timestamp [UCT]: 2025-03-24 15:22:43 Age [y:d:h:m:s]: 00:314:03:34:00
Block: 1246343 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222180 RingCT/type: yes/0
Extra: 0141fbf0e70ac106f0eb0a7cf97e29e05282a0a6573836a1f8355cc52c92456c62021100000002c6740958000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4930aa628858436ccbca8b6e460312a76a6b92835c36a97ad5cd75821d74ee4b 0.600000000000 1733344 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": 1246353, "vin": [ { "gen": { "height": 1246343 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4930aa628858436ccbca8b6e460312a76a6b92835c36a97ad5cd75821d74ee4b" } } ], "extra": [ 1, 65, 251, 240, 231, 10, 193, 6, 240, 235, 10, 124, 249, 126, 41, 224, 82, 130, 160, 166, 87, 56, 54, 161, 248, 53, 92, 197, 44, 146, 69, 108, 98, 2, 17, 0, 0, 0, 2, 198, 116, 9, 88, 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