Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b0ce6de17f671b05788fbca40e17a7a40bf6fbc3b2db9d96a9e0a2534ee4403

Tx prefix hash: 04db4573b4e7913e3249982d232bf40f31eb160828a5e4ffa0e5967ae35be249
Tx public key: ae0b96dafd608c17d756fc63557132d5f82c1073815a85198a09f67b80a339e5
Timestamp: 1735269051 Timestamp [UCT]: 2024-12-27 03:10:51 Age [y:d:h:m:s]: 00:085:12:39:46
Block: 1184014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60921 RingCT/type: yes/0
Extra: 01ae0b96dafd608c17d756fc63557132d5f82c1073815a85198a09f67b80a339e5021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8513e40cbce65bb9bf0e11f2652db288c90751217f41e80e0557af793a157a6a 0.600000000000 1670465 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": 1184024, "vin": [ { "gen": { "height": 1184014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8513e40cbce65bb9bf0e11f2652db288c90751217f41e80e0557af793a157a6a" } } ], "extra": [ 1, 174, 11, 150, 218, 253, 96, 140, 23, 215, 86, 252, 99, 85, 113, 50, 213, 248, 44, 16, 115, 129, 90, 133, 25, 138, 9, 246, 123, 128, 163, 57, 229, 2, 17, 0, 0, 0, 3, 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