Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7dc4a593ad9f1b36f0c57e1dfee21de5cc419d456df271bbc009a82ee5a11cd2

Tx prefix hash: ed24ca014bfc380d4396aec0adb374a63165a1330047fc27aade509aa6dda850
Tx public key: 3840b23db8dded22707c3828d64d98494d5e820e402e8a13a63bf7242e580bc6
Timestamp: 1733809780 Timestamp [UCT]: 2024-12-10 05:49:40 Age [y:d:h:m:s]: 00:117:07:40:49
Block: 1171946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83624 RingCT/type: yes/0
Extra: 013840b23db8dded22707c3828d64d98494d5e820e402e8a13a63bf7242e580bc6021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3bd86f5911c731d30af98aab68399ae2e7f86e30c0b45d2db9e6eaa7e7808a3 0.600000000000 1657773 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": 1171956, "vin": [ { "gen": { "height": 1171946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3bd86f5911c731d30af98aab68399ae2e7f86e30c0b45d2db9e6eaa7e7808a3" } } ], "extra": [ 1, 56, 64, 178, 61, 184, 221, 237, 34, 112, 124, 56, 40, 214, 77, 152, 73, 77, 94, 130, 14, 64, 46, 138, 19, 166, 59, 247, 36, 46, 88, 11, 198, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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