Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c74067f1ebde72b4c733169202f757d409b3dc53d7e1beaac613cf4484dab104

Tx prefix hash: d3987b9dbd2d4c1aa0db3ab7cf204b967813c49510224cd9b26ca1dd72b28f25
Tx public key: bedc213e70d2b759179ef8e84385361132aa3621eb3c97859cf71f4330b9a76c
Timestamp: 1695247292 Timestamp [UCT]: 2023-09-20 22:01:32 Age [y:d:h:m:s]: 01:200:05:25:21
Block: 852533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404168 RingCT/type: yes/0
Extra: 01bedc213e70d2b759179ef8e84385361132aa3621eb3c97859cf71f4330b9a76c021100000001faf35c9c000000000000000000

1 output(s) for total of 0.918764742000 dcy

stealth address amount amount idx
00: 44023b87bfe0c65491e5c1a791780fc15e523e26d6f7311e5e7e0edba0bc59ce 0.918764742000 1306377 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": 852543, "vin": [ { "gen": { "height": 852533 } } ], "vout": [ { "amount": 918764742, "target": { "key": "44023b87bfe0c65491e5c1a791780fc15e523e26d6f7311e5e7e0edba0bc59ce" } } ], "extra": [ 1, 190, 220, 33, 62, 112, 210, 183, 89, 23, 158, 248, 232, 67, 133, 54, 17, 50, 170, 54, 33, 235, 60, 151, 133, 156, 247, 31, 67, 48, 185, 167, 108, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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