Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98e239c9a0499498cecfe37dab1c2a1c9599f5089e95f7fe6969602b71fa8b76

Tx prefix hash: 551affd5c17fab4ae398277fcaf4a723239bd2c2d16a9a25e0fe318dfc10e337
Tx public key: 2875270a94b583c700da28cf54b0fa6fcaf9bfa8164ffaf506ffd00c39d1dfc8
Timestamp: 1737800420 Timestamp [UCT]: 2025-01-25 10:20:20 Age [y:d:h:m:s]: 00:145:01:49:39
Block: 1204933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103399 RingCT/type: yes/0
Extra: 012875270a94b583c700da28cf54b0fa6fcaf9bfa8164ffaf506ffd00c39d1dfc80211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 261fd0b3b79d0eac9c541d1caf779832facea4466d4fc2cf5c9c7442781423b4 0.600000000000 1691628 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": 1204943, "vin": [ { "gen": { "height": 1204933 } } ], "vout": [ { "amount": 600000000, "target": { "key": "261fd0b3b79d0eac9c541d1caf779832facea4466d4fc2cf5c9c7442781423b4" } } ], "extra": [ 1, 40, 117, 39, 10, 148, 181, 131, 199, 0, 218, 40, 207, 84, 176, 250, 111, 202, 249, 191, 168, 22, 79, 250, 245, 6, 255, 208, 12, 57, 209, 223, 200, 2, 17, 0, 0, 0, 4, 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