Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ca67f4f457accd3c857aad05eccab18584811fef409cf32f358154de4e441dc

Tx prefix hash: 59550d31c44b362ee7ac99614a4a51f551073c8c8fbf924ffc03fc6ec2b6fe1e
Tx public key: 03d2045b703b31ec2a272459d0c41a824f362a7e5a5440f04bf9ff0f5cf89b3a
Timestamp: 1699533854 Timestamp [UCT]: 2023-11-09 12:44:14 Age [y:d:h:m:s]: 01:090:06:02:24
Block: 887890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325660 RingCT/type: yes/0
Extra: 0103d2045b703b31ec2a272459d0c41a824f362a7e5a5440f04bf9ff0f5cf89b3a0211000000034b8f5122000000000000000000

1 output(s) for total of 0.701539050000 dcy

stealth address amount amount idx
00: c2e5a8782b26a0a0e98b9690fcc82d7c869d078208d063d3ceb2082eebdd67a6 0.701539050000 1343797 of 0

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": 887900, "vin": [ { "gen": { "height": 887890 } } ], "vout": [ { "amount": 701539050, "target": { "key": "c2e5a8782b26a0a0e98b9690fcc82d7c869d078208d063d3ceb2082eebdd67a6" } } ], "extra": [ 1, 3, 210, 4, 91, 112, 59, 49, 236, 42, 39, 36, 89, 208, 196, 26, 130, 79, 54, 42, 126, 90, 84, 64, 240, 75, 249, 255, 15, 92, 248, 155, 58, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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