Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1e3b91e785075b60fe97dd91de062f82a1126a5e22571cf7004aa26cab518f1

Tx prefix hash: ad94d9072935ba9c94a487d9ebf45fd45a924d6a0beb7088b8e26a960d121e16
Tx public key: 2edb19c939a81aa3b5d5802102fbd2d639421b7605330370056ec52a0dad72b0
Timestamp: 1698209256 Timestamp [UCT]: 2023-10-25 04:47:36 Age [y:d:h:m:s]: 01:145:00:34:19
Block: 877116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364649 RingCT/type: yes/0
Extra: 012edb19c939a81aa3b5d5802102fbd2d639421b7605330370056ec52a0dad72b0021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.761641502000 dcy

stealth address amount amount idx
00: 854e1ddc610a24f41d0ec8cbf84dc9f5be4e726c0090dd5413dc685e54eeb9b4 0.761641502000 1332476 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": 877126, "vin": [ { "gen": { "height": 877116 } } ], "vout": [ { "amount": 761641502, "target": { "key": "854e1ddc610a24f41d0ec8cbf84dc9f5be4e726c0090dd5413dc685e54eeb9b4" } } ], "extra": [ 1, 46, 219, 25, 201, 57, 168, 26, 163, 181, 213, 128, 33, 2, 251, 210, 214, 57, 66, 27, 118, 5, 51, 3, 112, 5, 110, 197, 42, 13, 173, 114, 176, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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