Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e5e1c2fc3b08872b4ff238637bc35e36c403864f7a7552cb17a2d27d0c1a4d2

Tx prefix hash: 3831d2ac1b94dcf772578504ed10dca3be052fc47d3cfe0df4fe5356bf675fd4
Tx public key: b810b58f84876f58305ff4840ec59e3ca52f0cc5e9a5060196ee161208784dd7
Timestamp: 1725731609 Timestamp [UCT]: 2024-09-07 17:53:29 Age [y:d:h:m:s]: 00:168:17:08:33
Block: 1105075 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120375 RingCT/type: yes/0
Extra: 01b810b58f84876f58305ff4840ec59e3ca52f0cc5e9a5060196ee161208784dd702110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 324a0788a961ec2b67fd1d96611f5a00fc42b6735a8d3f6fc080eacf0fb9d95b 0.600000000000 1582412 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": 1105085, "vin": [ { "gen": { "height": 1105075 } } ], "vout": [ { "amount": 600000000, "target": { "key": "324a0788a961ec2b67fd1d96611f5a00fc42b6735a8d3f6fc080eacf0fb9d95b" } } ], "extra": [ 1, 184, 16, 181, 143, 132, 135, 111, 88, 48, 95, 244, 132, 14, 197, 158, 60, 165, 47, 12, 197, 233, 165, 6, 1, 150, 238, 22, 18, 8, 120, 77, 215, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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