Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91bcdaae2a0d352d9111a20f380f1196cd063e426000654e8dfa5a4bef4f0672

Tx prefix hash: 42f2d81f7f6e12809bcba761f6cff7aa1d051f12a45e70cb7a8ec1372a32cf29
Tx public key: 32ae32ddcf28c978987eff113da1aad2133ed2db30a5b7b083dc105c0543ef82
Timestamp: 1721126666 Timestamp [UCT]: 2024-07-16 10:44:26 Age [y:d:h:m:s]: 00:259:19:35:34
Block: 1066916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185582 RingCT/type: yes/0
Extra: 0132ae32ddcf28c978987eff113da1aad2133ed2db30a5b7b083dc105c0543ef82021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9013f186154a892fe4b57d6cd6a54b1285b1b88df94cb9a133a11f436523f065 0.600000000000 1537593 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": 1066926, "vin": [ { "gen": { "height": 1066916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9013f186154a892fe4b57d6cd6a54b1285b1b88df94cb9a133a11f436523f065" } } ], "extra": [ 1, 50, 174, 50, 221, 207, 40, 201, 120, 152, 126, 255, 17, 61, 161, 170, 210, 19, 62, 210, 219, 48, 165, 183, 176, 131, 220, 16, 92, 5, 67, 239, 130, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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