Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5374cf6e12fde178347c10f98fd4e9ec0451a7169246c9621885bc7685fb41b7

Tx prefix hash: 16d55bf68c6751f3a4c08bd91f69403a7db904c228957b7d4bcdb5f58ce2f571
Tx public key: 5900a0efc4b527d7e0e946a776c5f8c594d45b5f021f047a68cfb810e3b7fa6a
Timestamp: 1730272176 Timestamp [UCT]: 2024-10-30 07:09:36 Age [y:d:h:m:s]: 00:025:06:31:55
Block: 1142645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18077 RingCT/type: yes/0
Extra: 015900a0efc4b527d7e0e946a776c5f8c594d45b5f021f047a68cfb810e3b7fa6a02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a84fe4eb99f1b92768fedf957046f610cd6c85695fa1819f3e58d76057fa69e 0.600000000000 1626500 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": 1142655, "vin": [ { "gen": { "height": 1142645 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a84fe4eb99f1b92768fedf957046f610cd6c85695fa1819f3e58d76057fa69e" } } ], "extra": [ 1, 89, 0, 160, 239, 196, 181, 39, 215, 224, 233, 70, 167, 118, 197, 248, 197, 148, 212, 91, 95, 2, 31, 4, 122, 104, 207, 184, 16, 227, 183, 250, 106, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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