Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9074455edba14927e27846329860b5d9dea4f86b75f8b6c7f51a821f22ffc7d

Tx prefix hash: a5e16f2a5161a8fffc7a4926e329ee1ffebf0f54c87db12d66310be380b6021a
Tx public key: 052a7e4f08d2db82f946fcb0f20afc99b1971dd319d0b85fcf1036fe01673b80
Timestamp: 1736193365 Timestamp [UCT]: 2025-01-06 19:56:05 Age [y:d:h:m:s]: 00:109:00:30:59
Block: 1191672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77714 RingCT/type: yes/0
Extra: 01052a7e4f08d2db82f946fcb0f20afc99b1971dd319d0b85fcf1036fe01673b8002110000000e1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81cb9c2c7384cdbac7300ed72da60dff596be77e3dac752f3756f04a7ce2ac57 0.600000000000 1678213 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": 1191682, "vin": [ { "gen": { "height": 1191672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81cb9c2c7384cdbac7300ed72da60dff596be77e3dac752f3756f04a7ce2ac57" } } ], "extra": [ 1, 5, 42, 126, 79, 8, 210, 219, 130, 249, 70, 252, 176, 242, 10, 252, 153, 177, 151, 29, 211, 25, 208, 184, 95, 207, 16, 54, 254, 1, 103, 59, 128, 2, 17, 0, 0, 0, 14, 31, 10, 83, 235, 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