Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd6b2ea1d6a17b7b3d3bad0dd63c924d8f3a8a98e2047eb38c18bb358a8d183b

Tx prefix hash: 76dff61cb94167db31471344549030e7cb2dc0f2bad364f43bff6d87efc7c3b7
Tx public key: 8e43b9761097c0fcf2cf0284eb3e0b6cae3906ccc4e9efaca2aa21df9946037f
Timestamp: 1719330941 Timestamp [UCT]: 2024-06-25 15:55:41 Age [y:d:h:m:s]: 00:264:11:03:20
Block: 1052000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188975 RingCT/type: yes/0
Extra: 018e43b9761097c0fcf2cf0284eb3e0b6cae3906ccc4e9efaca2aa21df9946037f021100000002d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bfa8c3a3fbd7428649dd01262684056ce610b9f24917b1fbd98281fe61407be 0.600000000000 1522321 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": 1052010, "vin": [ { "gen": { "height": 1052000 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bfa8c3a3fbd7428649dd01262684056ce610b9f24917b1fbd98281fe61407be" } } ], "extra": [ 1, 142, 67, 185, 118, 16, 151, 192, 252, 242, 207, 2, 132, 235, 62, 11, 108, 174, 57, 6, 204, 196, 233, 239, 172, 162, 170, 33, 223, 153, 70, 3, 127, 2, 17, 0, 0, 0, 2, 215, 73, 245, 17, 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