Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d243b6b8b686ec124d728ba3086afd2c54208fba87300d87080e628d2da318e

Tx prefix hash: 25e62e2dd8efeb2b50d4c01255dad5685b7a4bf3531639870c8c8c2d8ba78803
Tx public key: bfc7fc105c3120c6fba77580aee1c2916d4c64f70fb98aee78cc35c6bcc89f65
Timestamp: 1712597538 Timestamp [UCT]: 2024-04-08 17:32:18 Age [y:d:h:m:s]: 01:273:20:04:20
Block: 996152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 454495 RingCT/type: yes/0
Extra: 01bfc7fc105c3120c6fba77580aee1c2916d4c64f70fb98aee78cc35c6bcc89f6502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72787a0dbeaca59723780869bfdc1d9ea0dc8afd4df91b196192961ea62ee75d 0.600000000000 1456568 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": 996162, "vin": [ { "gen": { "height": 996152 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72787a0dbeaca59723780869bfdc1d9ea0dc8afd4df91b196192961ea62ee75d" } } ], "extra": [ 1, 191, 199, 252, 16, 92, 49, 32, 198, 251, 167, 117, 128, 174, 225, 194, 145, 109, 76, 100, 247, 15, 185, 138, 238, 120, 204, 53, 198, 188, 200, 159, 101, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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