Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31352b024c399825b6a636b070fc998b5d3156759ab43da4a1af235ea5051f1a

Tx prefix hash: f77e592050aa7502c5dba9600ac346080d5fb4133d2c8c3eae03757a1868eb6b
Tx public key: a09176d74c28645e4b7eb197648ba68df41a53a346ff79f0c7739097cc2e1b66
Timestamp: 1744238075 Timestamp [UCT]: 2025-04-09 22:34:35 Age [y:d:h:m:s]: 00:269:11:44:21
Block: 1257997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190414 RingCT/type: yes/0
Extra: 01a09176d74c28645e4b7eb197648ba68df41a53a346ff79f0c7739097cc2e1b6602110000000a6c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 564e8c51ff65671b77588a4138baf8dd0ef3ae2c6f573ea4ddb31b15d3303d6e 0.600000000000 1745128 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": 1258007, "vin": [ { "gen": { "height": 1257997 } } ], "vout": [ { "amount": 600000000, "target": { "key": "564e8c51ff65671b77588a4138baf8dd0ef3ae2c6f573ea4ddb31b15d3303d6e" } } ], "extra": [ 1, 160, 145, 118, 215, 76, 40, 100, 94, 75, 126, 177, 151, 100, 139, 166, 141, 244, 26, 83, 163, 70, 255, 121, 240, 199, 115, 144, 151, 204, 46, 27, 102, 2, 17, 0, 0, 0, 10, 108, 152, 170, 61, 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