Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e089791d141f778911bbc0b40933fc50bd3acf83138fd88f18d663463c786d2

Tx prefix hash: 77ffb829e91fb331cd85a0e4c93836665df2f01aa8cb6bd6eca3fc11390b5ed7
Tx public key: 8d3ebc614c13a97b3d31309dbe2593b59e3a7b073c54578a4f5726eac16c04bf
Timestamp: 1741601485 Timestamp [UCT]: 2025-03-10 10:11:25 Age [y:d:h:m:s]: 00:254:13:38:25
Block: 1236189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179673 RingCT/type: yes/0
Extra: 018d3ebc614c13a97b3d31309dbe2593b59e3a7b073c54578a4f5726eac16c04bf0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ff2012531e76634d90503bdf33af14533ba62821599ddbb7c0fe1432d3e9aba 0.600000000000 1723134 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": 1236199, "vin": [ { "gen": { "height": 1236189 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ff2012531e76634d90503bdf33af14533ba62821599ddbb7c0fe1432d3e9aba" } } ], "extra": [ 1, 141, 62, 188, 97, 76, 19, 169, 123, 61, 49, 48, 157, 190, 37, 147, 181, 158, 58, 123, 7, 60, 84, 87, 138, 79, 87, 38, 234, 193, 108, 4, 191, 2, 17, 0, 0, 0, 1, 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