Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68e9d68a762bd959bd1274fb954aa7c6a0725169666a60fb82386c216be60ac8

Tx prefix hash: 7a0b499a92302c87596ea41c4c26efe3dc610b4d5723cd2d46867ff628be760f
Tx public key: 7fa59f39cc9cfa261c7ad6a029cfdb2a822aa0761da9d4ade910ab4429fb60ee
Timestamp: 1717028359 Timestamp [UCT]: 2024-05-30 00:19:19 Age [y:d:h:m:s]: 01:190:02:21:52
Block: 1032927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394463 RingCT/type: yes/0
Extra: 017fa59f39cc9cfa261c7ad6a029cfdb2a822aa0761da9d4ade910ab4429fb60ee0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acafc7e9939413552f97475d639c454e0316803a60f0ec2ef399d0d641448317 0.600000000000 1501384 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": 1032937, "vin": [ { "gen": { "height": 1032927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acafc7e9939413552f97475d639c454e0316803a60f0ec2ef399d0d641448317" } } ], "extra": [ 1, 127, 165, 159, 57, 204, 156, 250, 38, 28, 122, 214, 160, 41, 207, 219, 42, 130, 42, 160, 118, 29, 169, 212, 173, 233, 16, 171, 68, 41, 251, 96, 238, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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