Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c5f407a8334da170e386fb49d44d6fd814a4b38e0fce9977129c63ecfb19cfc

Tx prefix hash: 4d1538e657798aefd0f01b972c01dd5dff3f0dc56bccafe55c235ab8e499bdeb
Tx public key: a6781f3014aa8f6b8089638115bb59d8e472ed70567065304a694c745086d8f1
Timestamp: 1712329637 Timestamp [UCT]: 2024-04-05 15:07:17 Age [y:d:h:m:s]: 01:207:22:07:22
Block: 993938 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407293 RingCT/type: yes/0
Extra: 01a6781f3014aa8f6b8089638115bb59d8e472ed70567065304a694c745086d8f10211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8c2c3f57ba1b56c05e5d6000a849cce15a076a8adb5eaca67d5b2ccf2556d4f 0.600000000000 1454334 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": 993948, "vin": [ { "gen": { "height": 993938 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8c2c3f57ba1b56c05e5d6000a849cce15a076a8adb5eaca67d5b2ccf2556d4f" } } ], "extra": [ 1, 166, 120, 31, 48, 20, 170, 143, 107, 128, 137, 99, 129, 21, 187, 89, 216, 228, 114, 237, 112, 86, 112, 101, 48, 74, 105, 76, 116, 80, 134, 216, 241, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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